[BF-032] GSC/Analytics dashboard 文档和运营检查表 - #91

Issue

Closes #58

Scope

• Add the growth dashboard runbook for weekly/monthly operations.
• Add SEO monitoring guidance for GSC, route families, query clusters, and technical SEO gates.
• Add a privacy-safe analytics policy for dashboard exports, provider requirements, and forbidden fields.

Implementation

• Added docs/growth/dashboard-runbook.md with required data-source access, north-star metrics, SEO/product dashboard metrics, weekly/monthly checklists, post-release monitoring, and issue feedback loop.
• Added docs/growth/seo-monitoring.md with GSC query clusters, URL families, weekly review flow, monthly content review, technical SEO gates, and escalation levels.
• Added docs/privacy/analytics-policy.md defining allowed aggregate signals, prohibited data, provider requirements, search rules, file/tool data rules, export rules, and review checklist.

Acceptance Criteria

• 文档包含指标定义。
• 文档包含每周检查步骤。
• 文档列明需要授权的数据源。
• 文档列明禁止采集字段。
• npm run lint 不因文档失败。

Validation

• npm run lint - PASS
• npm run test - PASS, 224 files / 1124 tests
• npm run validate - PASS, including analytics taxonomy, privacy copy, i18n, security, SEO, bundle, and type gates
• npm run build - PASS, generated 1401 static pages; canonical/hreflang, metadata localization, JSON-LD, rendered i18n copy, localized content, and service worker post-build gates passed
• git diff --check - PASS after trailing blank-line cleanup

Manual Checks

• Confirmed issue [BF-032] GSC/Analytics dashboard 文档和运营检查表 #58 is open before starting this PR.
• Confirmed this is a pure documentation PR.
• Reviewed the docs for actionable weekly/monthly operating steps.
• Scanned docs for sensitive analytics terms and confirmed they appear only in prohibition/privacy contexts.

Privacy Check

• 不采集工具输入
• 不采集工具输出
• 不新增未披露的外部请求
• 不持久化敏感 payload
• Documentation explicitly forbids collecting input, output, JWTs, tokens, secrets, log bodies, file names, file contents, image contents, hashes, full URLs, cookies, user IDs, session IDs, and fingerprints.

Screenshots / Evidence

• Pure documentation PR; command output from validation suite above is the evidence.